Skip to content

Add missing project to wolverine.slnx#2575

Closed
saithis wants to merge 1 commit intoJasperFx:mainfrom
saithis:fix-solution
Closed

Add missing project to wolverine.slnx#2575
saithis wants to merge 1 commit intoJasperFx:mainfrom
saithis:fix-solution

Conversation

@saithis
Copy link
Copy Markdown
Contributor

@saithis saithis commented Apr 23, 2026

No description provided.

@saithis
Copy link
Copy Markdown
Contributor Author

saithis commented Apr 23, 2026

Without it wolverine doesn't compile, since it can't find the project.

jeremydmiller added a commit that referenced this pull request Apr 26, 2026
…ject-in-slnx

Add Wolverine.SourceGeneration to slnx (supersedes #2575)
jeremydmiller added a commit to rmasciarella/wolverine that referenced this pull request Apr 26, 2026
After JasperFxGH-2575 added Wolverine.SourceGeneration to wolverine.slnx,
`dotnet build wolverine.slnx --framework net9.0` started failing with
NETSDK1005 because the analyzer project only targets netstandard2.0
(required for Roslyn analyzer loadability). The error doesn't appear in
unconstrained builds because the project naturally selects its single
TargetFramework, but CI and local commands that pin a framework hit it.

The project is already pulled in transitively as an analyzer via
Wolverine.csproj's ProjectReference (OutputItemType="Analyzer",
ReferenceOutputAssembly="false"), so it gets built whenever Wolverine
itself does. Marking it Build="false" in the slnx — same pattern used
for build/build.csproj — keeps it visible in the IDE solution view but
skips it from solution-level builds, sidestepping the framework
resolution mismatch.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jeremydmiller
Copy link
Copy Markdown
Member

Got it w/ a different PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants